You are here: System operations > High availability > Quiesce > Quiesce using slow drain

Quiesce using slow drain

When using slow drain for quiesce on a highly available system, the following steps occur on a Pega Platform server when the quiesce process is enabled:

  1. The default timeout for passivation is reduced, referred to as an accelerated passivation period.
  2. Users are placed in a passivation queue.
  3. The system stops non-essential agent processing for quiesce and all listeners, with the exception of message-driven bean (MDB) listeners. (The application server should be configured to ensure that no MDB invocations occur.)
    Note: System critical agents remain active during this step.
  4. When the active user requestor count drops to 0, the system sets the server state to "Quiesce Complete" and the Pega Platform server is ready for maintenance.

Note: All Pega Platform servers on a physical or virtual machine must be quiesced for maintenance on the machine.